Mapping Different Software Architecture Paradigms to Different Integration Techniques: Highlighting Driving and Restraining Forces for Each Paradigm

Technical agility refers to the ability to quickly change the type and flow of information within an enterprise. Technical agility parameters are affected by enterprise architecture. IT advance has not yet satisfied business requirements due to improper software architectures. SOA addresses technical agility requirements by presenting composability, modularity, and loose coupling concepts as services that wrap underlying IT infrastructure, databases, and legacy systems and present them via standard interface. There is a need to stabilize IT infrastructure rather than developing new ones and SOA enables this stabilization. Enterprises should balance IT to become better positioned and more agile. Services are the building Blocks of an agile enterprise. This paper discusses the importance of enterprise architecture in meeting systems’ non-functional requirements and examines different software architecture paradigms, driving and restraining forces for each one in meeting systems integration as one of the most desirable requirement. Integration has different techniques, and different software architecture paradigms can address different techniques. This paper presents a proposed mapping of different software architecture paradigms to different integration techniques while highlighting driving forces that encourages software architects to utilize it and restraining forces that discourages architects from utilizing them.